@Addison Scummvm have a cloud option to upload the saves automaticaly but i haven't test it yet. You will find this if you open Scummvm gui : Global Options >> Cloud.

Solved!

So the issue was, it was using ~/.config/eduke32 as the config directory where everything went. Even changing the executable's filename did not change this location used so it must be hard coded in the application somewhere (even if it's just "this application is called eduke32" and then it just used "whatever the application calls itself" as the config folder, that is what it is using.) So there really is no way to change the save location... [one more thing I don't think I tried: renaming the folder in which the executable exists -- but it doesn't matter because even if it did work (I have doubts), I think the solution I ended up with is more elegant than quadruplicating the executable folder four different times for four different games.]

...EXCEPT! That location is, already, just a symlink to the config folder in /opt/retropie/configs/ports/duke3d. So, inside of that folder, I made three new folders: dc, nw, and vacation. Then I edited my launch scripts to re-link the .config/eduke32 link. At first I got an error: "failed to create symbolic link: file exists." So I tried it with the -f(orce) option. Got a different error: "cannot overwrite directory." Finally, I decided to just remove the existing link before creating a new one (and then -f was no longer needed.) That worked! Now, before a game is launched, the link in ~/.config is reconfigured to point at the correct subfolder, and then saves and configs are stored separately per-game.

After the game exits, I set the link back to its original location and, for good measure, I move the log in $HOME to the config folder first.

Example duke3d-vacation.sh launch script:

#! /bin/bash rm ~/.config/eduke32 ln -s /opt/retropie/configs/ports/duke3d/vacation ~/.config/eduke32 "/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "duke3d" "-j /home/pi/RetroPie/roms/ports/duke3d -g vacation/vacation.grp -x vacation/game.con -j /home/pi/RetroPie/roms/ports/duke3d/vacation" mv ~/eduke32.log ~/.config/eduke32 rm ~/.config/eduke32 ln -s /opt/retropie/configs/ports/duke3d ~/.config/eduke32

For the Original duke3d.sh script I still set the link to .../configs/ports/duke3d before launch, just in case anything prior left it in weird shape, but obviously I don't have to "fix" it after since that's the original default location anyway.

Hi there,

So I left my Raspberry Pi alone for a month and when I came back to it I started fresh. I think the problem was with my HDD.

So I think my HDD was previously formatted to exFAT file system. The only options I had were NTFS and exFAT. I found this person on youtube called Eta Prime and his videos were a big help, especially this one:

It explains how to format your drive to FAT32

I flashed the image to the SD again and formatted my HDD to FAT32 and added the "retropie-mount" folder as shown in the video.

Then I searched some more videos on his channel of which bios were needed for the different emulators and how to add the games.

I found out how to "unECM" the ECM files from my PlayStation games and I'd say at the moment about 90% of the games work and I can save using the save state feature + via the in-game save mechanics.

The emulators I have used up to this point are: GB, GBC, GBA, NES, SNES, N64, Megadrive and PS1.

So yes, I'd say the problems are now solved. Maybe one more thing I'd like to try is activating my RetroAchievements account so I can earn achievements on some of the games. I got it to work previously, but I don't know how anymore because it's been over a month ago.

Big shout out to Eta Prime. Check his channel here:

https://www.youtube.com/channel/UC_0CVCfC_3iuHqmyClu59Uw

Yes, I believe I did the same thing with the configs text, sorry I’m pretty new to all this. Just trying to shed some light on something I was reading about the last few days.

edited /opt/retropie/configs/n64/mupen64plus.cfg
Like this:
#Path to directory where emulator save states (snapshots) are saved. If this is blank, the default #value of ${UserConfigPath}/save will be used
SaveStatePath = "/home/pi/RetroPie/roms/n64"
#Path to directory where SRAM/EEPROM data (in-game saves) are stored. If this is blank, the default #value of ${UserConfigPath}/save will be used
SaveSRAMPath = "/home/pi/RetroPie/roms/n64"

That’s handy to know, when I moved my lad’s system from a zero to a pi3, I had issues with saves. Thanks

Duhhhhhh... Solution is here.

Can't delete this, but sorry for wasting server space...

In case anyone searches this in the future...

Go into ScummVM and navigate to Options >> Paths and change the path location to whatever you'd like. For me it was ./roms/ScummVM/saves/. To recover your previous saves, navigate to /opt/configs/retropie/ScummVM/saves/ with a program like Filezilla and copy them to the desktop then move them to your USB for example. Another option would be to, in the command line, use the mv -i /opt/retropie/configs/ScummVM/saves ./roms/ScummVM/saves/ for example.

before you all ask... 3 amp power supply (because contrary to Raspberry Pi's requirements 2.5 amps is not enough for anybody hence the lightning bolt in the corner for most people) 1200MHz overclock speed, and both heatsinks & fans cooling it.

Thank you,

that sounds much easier than what we did. I'll have to try that one out :)

@herb_fargus Oh sorry I did not know that this was also forbidden :-/ I edited it out

@VTHokiEE
I think it depends on which emulator made those save files. Like if you did a save state with lr-vba-next and try to load it with lr-gpsp, it will not work but go back to lr-vba-next and it can read them again.

@erlloyd said in Native N64 save sometimes .fla:

Is there a way to configure lr-mupen64plus to use glide64 for video emulation?

No, but 'lr-GLupeN64' uses glide64. However, you'll be sacrificing the performance you get from the standalone 'Mupen64plus'.

It looks like you are referring to retroarch.cfg based controller configs (to generate those I'd let ES do it, not the manual way it looks like you have.)

Also, you can see here that the emulator you are using wont use those config files:
https://github.com/retropie/retropie-setup/wiki/Nintendo-64

Oh for sure! This is just nice to be able to hit a button and let it do it's thing. It will be the same to restore soon.